Is there an easy naming policy to distinguish plugins built with wxWidgets 3.11? Do I need to make a new GitHub repository for each 3.1.1 plugin to avoid confusion?

To reiterate: You will see a branch “o486” in the OpenCPN github repo. That branch was captured at the point of release of 4.8.6. It will build the current production release, and will be forked again to contain critical backports if required. New work goes on in “master”.

The opencpn.org download page will generally point to “master” of the plugin repo for the source link. Presumably source builders will know which branch they need to pull for local builds. The download page will also point to built binaries that are compatible with the current release of base OCPN, whatever that may be at the time.

If/when we have a Beta underway that breaks compatibility, there will be another section of the .org site that provides links to plugin Beta binaries ready and available for test with the Beta base.

Note: We now like to include an indication for the OpenCPN Minumum Version Number in the filename for the plugin. For example, weather_routing_pi-1.12.1-ov42-win32.exe would be for Opencpn v4.2 up to v4.8.8, when we had an increment in Opencpn to v5.0.

At that time (Opencpn v5.0) we changed from wxWidgets 3.0.2 to wxWidgets 3.1.2. Now the weather_routing plugins for Opencpn 5.00 are named weather_routing_pi-1.13.0-ov50-win32.exe